PoC: public transaction notes #4693
Conversation
Branch preview✅ Deploy successful! Website: Storybook: |
Coverage report
Show new covered files 🐣
Show files with reduced coverage 🔻
Test suite run success1752 tests passing in 237 suites. Report generated by 🧪jest coverage report action from 96a1684 |
📦 Next.js Bundle Analysis for safe-wallet-webThis analysis was generated by the Next.js Bundle Analysis action. 🤖
|
| Page | Size (compressed) |
|---|---|
global |
1012.91 KB (🟡 +291 B) |
Details
The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.
Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis
If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!
Seven Pages Changed Size
The following pages changed size from the code in this PR compared to its base branch:
| Page | Size (compressed) | First Load |
|---|---|---|
/apps/open |
53.61 KB (-1 B) |
1.04 MB |
/transactions |
96.57 KB (-1 B) |
1.08 MB |
/transactions/history |
96.53 KB (-1 B) |
1.08 MB |
/transactions/messages |
58.3 KB (-1 B) |
1.05 MB |
/transactions/msg |
54.55 KB (-1 B) |
1.04 MB |
/transactions/queue |
47.4 KB (-1 B) |
1.04 MB |
/transactions/tx |
46.76 KB (-1 B) |
1.03 MB |
Details
Only the gzipped size is provided here based on an expert tip.
First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.
Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis
Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this.
|
|
||
| const [data] = useAsync(() => { | ||
| if (!safeTxHash || !txService) return | ||
| return fetch(`${txService}/api/v1/multisig-transactions/${safeTxHash}`).then((res) => res.json()) |
There was a problem hiding this comment.
I'm using the tx-service directly here because CGW doesn't mirror the origin field. It can be easily added there.
What it solves
This PR hijacks the
origin.namefield in proposed transactions to attach a custom note to a tx. To avoid collisions with actual Safe App names used for this purpose, the note is encoded as JSON.The note is then retrieved from the tx-service's
originfield and JSON-parsed.Adding a note:
from the transaction service from the origin field in TransactionDetails.
Displaying a note:
